Data transfer between devices

ABSTRACT

A method of implementing data transfer from a mobile device is described. The method comprises: (i) receiving positional information from the mobile device; (ii) receiving directional information from the mobile device; and (iii) receiving data from the mobile device. The method further comprises: (iv) ascertaining a receiving device based on the received directional information; and (v) providing the data received from the mobile device to the ascertained receiving device.

FIELD OF INVENTION

The present invention relates to data transfer between devices.

BACKGROUND OF INVENTION

In many environments, such as in business meetings, social meetings,gaming establishments (such as casinos), multi-player games (eitherphysical or virtual), and the like, it is desirable to be able to shareinformation with other people quickly and dynamically.

Although rapid communications between individuals has been improved bysocial media and communications facilities (for example, instantmessaging, status updating and tracking, sharepoints, and the like), itis still difficult to transfer data between individuals in a group in arapid manner, particularly if the group is changing dynamically or ifthe participants do not know each other.

SUMMARY OF INVENTION

Accordingly, the invention generally provides methods, systems,apparatus, and software for facilitating data transfer from a firstperson's mobile device to another device using positional and/ordirection information provided by the first person's device.

In addition to the Summary of Invention provided above and the subjectmatter disclosed below in the Detailed Description, the followingparagraphs of this section are intended to provide further basis foralternative claim language for possible use during prosecution of thisapplication, if required. If this application is granted, some aspectsmay relate to claims added during prosecution of this application, otheraspects may relate to claims deleted during prosecution, other aspectsmay relate to subject matter never claimed. Furthermore, the variousaspects detailed hereinafter are independent of each other, except wherestated otherwise. Any claim corresponding to one aspect should not beconstrued as incorporating any element or feature of the other aspectsunless explicitly stated in that claim.

According to a first aspect there is provided a method of implementingdata transfer from a mobile device, the method comprising:

(i) receiving positional information from the mobile device;

(ii) receiving directional information from the mobile device;

(iii) receiving data from the mobile device;

(iv) ascertaining a receiving device based on the received directionalinformation; and

(v) providing the data received from the mobile device to theascertained receiving device.

Steps (i) to (iii) may be implemented concurrently (for example, in thesame transmission) or in any desired order (for example, step (ii)first, then step (iii) then step (i)).

The positional information may be provided via a cellular system basedon the location of the mobile device as detected by the cellulartransmission system. Alternatively, the mobile device may provide thepositional information from an integrated global positioning systemwithin the mobile device.

The directional information may be ascertained by the mobile device.This may be implemented using an internal accelerometer, therebydetecting how a user of the mobile device is moving the mobile device.Alternatively, this may be implemented by the mobile device sensingpoints touched by the user of the mobile device on a touchscreen of themobile device, for example, by sensing the user swiftly flicking his/herfinger over the touchscreen surface.

The data received from the mobile device may relate to an image (such asa photograph or artwork), a document (such as a letter, email,spreadsheet, or presentation), a game (such as an activity performed bythe user of the mobile device), or any other information in electronicform.

Ascertaining a receiving device based on the received directionalinformation may include ascertaining a device located in the directionof motion provided by the user of the mobile device (for example, theuser may swiftly move the mobile device towards the receiving device, ormay apply a flicking motion of his/her finger to the touchscreen in thedirection of the receiving device). Alternatively, ascertaining areceiving device based on the received directional information mayinclude ascertaining a plurality of receiving devices selected by theuser of the mobile device in addition to the received directionalinformation from the mobile device.

Providing the data received from the mobile device to the ascertainedreceiving device may include providing the ascertained receiving devicewith an identification of the mobile device.

The method may include the step of registering the mobile device whenthe mobile device enters an interaction environment. The interactionenvironment may be relatively small, for example, within an office, anentertainment establishment, a stadium, or a home, where a localwireless network (such as one based on one of the 802.11 standards) isused. Alternatively, the interaction environment may be relativelylarge, for example, within a city, county, country, or globally, where awide area wireless network (such as the Internet or a satellite orcellular communications system) is used.

The step of registering the mobile device when the mobile device entersan interaction environment may be implemented by the user of the mobiledevice providing an identification to a management application, wherethe management application implements the steps described above. Themobile device may register automatically when it enters the interactionenvironment. The identification may comprise a telephone numberassociated with the mobile device. Alternatively, the identification maycomprise an email address, a username, a MAC address or other type ofunique hardware identifier, or the like.

The mobile device may comprise a cellular telephone, such as a so-called“smartphone”.

The method may further comprise the additional step of: receivingvelocity and/or acceleration information from the mobile device; and thestep of ascertaining a receiving device based on the receiveddirectional information may include ascertaining the receiving devicebased also on the received velocity and/or acceleration information.

The mobile device may provide the positional and/or directionalinformation via a defined interface.

The mobile device may execute a data sharing application (downloadablefrom a relevant application store for that type of device) that includesthe defined interface and that includes contact information forcommunicating with a management application appropriate for the mobiledevice's location and/or environment.

The data sharing application may provide a user of the mobile devicewith options for: sharing data (for example, opting in or opting out ofsharing data), groups available that are open to new participants,creating a new group, defining properties of the new group (for example,sports, discussion group, privacy settings), and the like.

The receiving device may comprise a mobile device (such as anothersmartphone) or a static device (such as a printer or a file server).

According to a second aspect there is provided a management applicationoperable to implement the steps of the first aspect.

The management application may be implemented as a cloud application.

According to a third aspect there is provided a method of implementingdata transfer from a mobile device, the method comprising:

(i) providing positional information about the mobile device to amanagement application;

(ii) providing directional information from the mobile device to themanagement application; and

(iii) providing data from the mobile device.

These steps may be implemented in any convenient order.

The information provided in steps (i) and (ii) may be provided via adefined interface using a downloaded application.

According to a fourth aspect there is provided a method of implementingdata transfer from a mobile device to a receiving device, the methodcomprising:

registering the mobile device;

receiving positional information from the mobile device;

receiving directional information from the mobile device;

receiving data from the mobile device;

identifying spatial positions of other registered devices;

selecting a receiving device from one of the registered devices based onthe received directional information and the spatial positions of theregistered devices; and

transferring the data received from the mobile device to the selectedreceiving device.

The selected receiving device may be a static device (such as a desktopcomputer, a printer, a file server, or the like) or a mobile device(such as a cellular telephone, an automobile, or the like).

For clarity and simplicity of description, not all combinations ofelements provided in the aspects recited above have been set forthexpressly. Notwithstanding this, the skilled person will directly andunambiguously recognize that unless it is not technically possible, orit is explicitly stated to the contrary, the consistory clausesreferring to one aspect are intended to apply mutatis mutandis asoptional features of every other aspect to which those consistoryclauses could possibly relate.

These and other aspects will be apparent from the following specificdescription, given by way of example, with reference to the accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic plan view of an office area in which data transferoccurs between mobile devices, according to one embodiment of thepresent invention;

FIG. 2 is a simplified block diagram of a mobile device for use with thesystem of FIG. 1;

FIG. 3 is a flowchart illustrating steps implemented by the mobiledevice of FIG. 2 to register with a management application associatedwith the office area of FIG. 1;

FIG. 4 is a flowchart illustrating steps implemented by an applicationexecuting on the mobile device of FIG. 2 to create a new share groupwith the management application associated with the office area of FIG.1;

FIG. 5 is a flowchart illustrating the steps implemented by theapplication executing on the mobile device of FIG. 2 as part of ameeting involving document sharing between devices; and

FIG. 6 is a flowchart illustrating the steps implemented by theapplication executing on the mobile device of FIG. 2 as part of a gameinvolving data transfer.

DETAILED DESCRIPTION

Reference will now be made to FIG. 1, which is a schematic plan view ofan office area 10 in which data transfer occurs between devices,according to one embodiment of the present invention.

In FIG. 1, the office area 10 comprises the following zones: a businessmeeting room 12, a games room 14, a cafeteria 16, an office seating area18, a print station 20, and a vending area 22 (the first three zones areillustrated by solid lines, the last three zones are illustrated bybroken lines).

A server 30 (referred to as a cloud server because the geographiclocation of the server 30 is not important) is provided that hosts amanagement application 32. The cloud server 30 may be inside or outsidethe office area 10.

Fifteen people 40 a-o (also referred to as “users”) are illustrated indifferent parts of the office area 10. Each of these persons 40 a-o hasa mobile device (not shown in FIG. 1 for clarity).

Reference will now also be made to FIG. 2, which is a simplified blockdiagram of a representative mobile device 50, similar to the mobiledevice carried by each person 40.

In this embodiment each mobile device 50 is a conventional cellulartelephone (cell phone) having a touch-sensitive display (referred to asa touchscreen) and Internet access. Such cell phones 50 are typicallyreferred to as smartphones.

In addition to specific components dedicated to telephony (microphone,loudspeaker, codec, cellular transceiver, and the like), which are notillustrated in FIG. 2, the smartphone 50 comprises a controller 52 andassociated memory 54, a touchscreen 56, an 802.11 wireless transceiver58, an accelerometer 60, a digital compass 62, and a GPS device 64. Thesmartphone 50 includes other components, but these are not essential toan understanding of this embodiment.

The smartphone 50 is a conventional smartphone (that includes thecomponents listed above) of the type provided by any one of variousvendors (such as Apple, Samsung, HTC, Nokia, Sony Ericsson (all trademarks of their respective owners)).

In addition to the conventional system software (not shown for clarity)provided with the smartphone 50 and resident in memory 54, thesmartphone 50 also executes a data sharing application 70 (downloadablefrom a relevant application store for that type of smartphone). The datasharing application 70 provides a defined management interface(illustrated schematically in FIG. 2 by ellipse 72) that communicateswith the management application 32 in the cloud server 30.

The data sharing application 70 also includes a communication object 74that stores details of how to communicate with the managementapplication 32 (such as an IP address and port number) and managescommunications between the management application 32 and the datasharing application 70.

The data sharing application 70 also includes a configuration object 76that stores data related to the user 40, allows the user 40 to requestcreation of sharing groups, stores information about the sharing groupsthe user 40 has joined, allows the user to set parameters for who canjoin a sharing group they have created, set privacy parameters, and thelike.

Referring again to FIG. 1, the management application 32 provides adefined device interface (illustrated schematically in FIG. 1 by ellipse80) that communicates with the data sharing application 70 executed byeach smartphone 50 carried by the users 40.

Reference will now be made to FIG. 3, which is a flowchart 100illustrating steps implemented by a smartphone 50 carried by a user 40in registering with the management application 32.

Initially, the user 40 downloads the data sharing application 70(referred to hereinafter as application 70) from an application store tothe user's smartphone 50 (step 102). The application 70 may be free orthere may be a charge for downloading and/or using the application 70.

The user 40 then installs the application 70 (step 104) after agreeingto whatever license terms are required to install and execute theapplication 70.

Once installed, the user 40 launches the application 70 and provides aunique identifier (for example, a username) to the application 70 (thismay comprise an email address, a telephone number, an IP address, or anyother unique identifier, such as a string of characters selected by theuser 40). The application 70 receives and stores this unique identifierin the configuration object 76 (step 106) (after confirming that theusername is indeed unique). In some embodiments the user 40 may have toprovide a unique identifier prior to downloading the application 70(that is, prior to step 102).

The user 40 then selects a register option presented by the application70 on the touchscreen 56, which the smartphone detects (step 108). Thecommunication object 74 then communicates with the managementapplication 32 on the server 30, via the defined device interface 80, toregister the user 40 with the management application 32 (step 110).

Part of the registration process of step 110 involves the managementapplication 32 receiving registration information from the communicationobject 74 about (i) the location of the smartphone 50 (from the GPSdevice 64), (ii) share groups that the user 40 is a member of (from theconfiguration object 76), and (iii) any services that the user'ssmartphone 50 provides (from the configuration object 76). The user'ssmartphone 50 does not provide any services, but if the registereddevice was a printer (such as the printer at print station 20), then theservices provided may include printing. The management application 32stores this registration information.

Once the user 40 has been registered by the management application 32,the management application 32 provides the application 70 withconfirmation of registration, which the application 70 receives (step112). The application 70 then notifies the user 40 that registration hasbeen successful (step 114).

The user 40 is now registered with the management application 32. Theuser 40 can now transfer data from his/her smartphone 50 to otherdevices registered with the management application 32, as will now bedescribed in three different scenarios (all provided merely by way ofillustration).

Scenario 1—Business Meeting

The first scenario involves the user 40 participating in a businessmeeting in the meeting room 12. As shown in FIG. 1, there are fourpeople in the meeting room 12, namely users 40 a to 40 d.

In this scenario, user 40 a desires to share a presentation with theother attendees (users 40 b,c,d) so that all four participants canmodify and update the presentation. Each of the users 40 a,b,c,d hasalready registered with the management application 32.

Reference will now be made to FIG. 4, which is a flowchart 130illustrating the steps performed at the user's smartphone 50 a (that is,the smartphone of user 40 a) to create a new share group restricted tothe participants in the meeting (namely, users 40 a,b,c, and d).

Initially, the user 40 a uses the application 70 on his/her smartphone50 a to create a new share group. This is achieved using a “create sharegroup menu option” (not shown) provided by the application 70. Theapplication 70 receives this share group creation request (step 132).

The application 70 then prompts the user 40 a to enter parametersrelating to the new share group (step 134). These parameters include:the group name (which is “business plan share group” in this example),the maximum size of the group (in this example it may be four people),and whether the group is public or private (it is private in thisexample).

The application 70 then receives these parameters (step 136), and thencommunicates this share group creation request (including the receivedparameters) to the management application 32 using the managementinterface 72 and the communication object 74 (step 138).

The management application 32 uses this received information to create anew share group with the requested name (“business plan share group”)and other requested properties. By default, the user 40 a is listed asthe group owner because he/she transmitted the request to create a newshare group.

The management application 32 then transmits a confirmation message tothe application 70, which confirms to the user 40 a that the share grouphas been created (step 140).

The application 70 then notifies the user 40 a that the new share grouphas been created (step 142) by the management application 32.

Once the share group has been created, the user 40 a can invite otherattendees to join the group. This can be achieved by the user 40 asending an email, instant message, or other communication to the otherthree participants 40 b,c,d with a link enabling them to join the group.Alternatively, the other three meeting participants can enter the sharegroup name (which is not published by the management application 32because it is a private meeting) and a meeting passcode (assigned by themanagement application 32 when the share group was created, or selectedby the user 40 a as part of the share group creation request).

Once all four participants have joined the meeting, they can freelyshare information between devices in the following way.

One user (for example, user 40 b) desires to share a presentation withanother participant (for example, user 40 c). To do this, while theapplication 70 is executing, the user 40 b selects the presentation tobe shared, points his device at user 40 c, and flicks the presentationtowards user 40 c by moving his finger over the touchscreen 56 in thedirection of the user 40 c.

Reference will now be made to FIG. 5, which is a flowchart 150illustrating the steps implemented by the application 70 in interpretingthis action by user 40 b.

Initially the application 70 detects that the presentation has beenselected (step 152).

The application 70 then detects that the user has made a flicking motionwith his finger across the touchscreen 56 (step 154). This is detectedbecause a sequence of contact points on the touchscreen 56 are detected(by the controller 52) that all lie on a generally straight line. Theapplication 70 interprets this action as meaning that the user 40 bdesires to transmit the selected presentation to the nearest device thatis generally in line with (on the trajectory of) this motion.

The application 70 ascertains the orientation of the device 50 b usingthe digital compass 62 (step 156).

The application 70 then transmits a data package to the managementapplication 32 via the management interface 72 and the communicationobject 74 (step 158). The data package comprises: (i) a copy of thepresentation, (ii) details of the orientation of the device 50 b whenthe user action occurred, and (iii) details of the type and direction ofthe user action (in this example, a continuous line was delineated byuser 40 b from a lower part of the touchscreen 56 to an upper part ofthe touchscreen 56 (if the touchscreen 56 is considered as a clockface,the movement would correspond to movement from 6 o'clock to 12 o'clock).

The management application 32 receives this data package via definedinterface 80 and uses the orientation of the device 50 b and thedirection of the user's action to ascertain which device should receivethe presentation. In this example, the user 40 b is part of a privateshare group, so the management application 32 identifies the participantdevice that is closest to the trajectory of the action performed by user40 b. In this example, it is user 40 c, so the management application 32transfers the copy of the presentation to device 50 c. The managementapplication 32 then notifies the application 70 that the presentationwas transferred to device 50 c. The application 70 receives thisnotification (step 160) and informs the user 40 b accordingly (step162).

The application 70 also has a menu option that allows a user 40 to senda data file to all participants in the share group. If this is selected,then once a user selects a data file, then any linear motion (other thana minimal touch by the user) will cause the data file to be transmittedto all participants. This enables all participants to receive the datafile quickly and easily.

Instead of delineating a line on the touchscreen 56, the user 40 mayflick his/her wrist towards the intended recipient. In such a case, theapplication 70 would detect a change in state of the accelerometer 60and then transmit this information as part of the data package.

Scenario 2—Interactive Game

The second scenario occurs in the games room 14. In this scenario thereare two registered users 40 e and 40 f who are playing a game. Theplayers register with the management application 32 in a similar way tothe first scenario. One of the registered users then creates a sharegroup that is public, but local to the games room 14 (in other words, auser 40 needs to be in the physical vicinity of the games room 14 toparticipate).

In this scenario, the management application 32 executes a two-persongame of virtual catch.

Reference will now be made to FIG. 6, which is a flowchart 170illustrating the steps implemented by the application 70 as part of thegame of virtual catch.

Initially, the management application 32 sends a data package to one ofthe registered devices (for example, 50 e). This registered device 50 ereceives the data package (step 172), which includes details of theobject (ball) being thrown (including its size and shape), thetrajectory of the ball, and the speed of the ball.

The user 40 e then tries to catch the ball by moving her device 50 e tothe spatial location to which the ball appears to be heading. Theapplication 70 monitors the accelerometer 60 and the digital compass 62(step 174) to ascertain if the user 50 e has “caught” the ball (that is,if the user 40 e has moved the device 50 e to where the ball would bebased on the ball's trajectory and speed) (step 176). If the user 40 esuccessfully “catches” the ball, then the application 70 displays theball on the touchscreen 56 (step 178); otherwise the application 70displays an image indicating that the ball was missed (step 180).

The user 40 e can then “throw” the ball to the other participant (user40 f). The application 70 monitors the accelerometer 60 and the digitalcompass 62 for changes that would indicate that the user 40 e hasattempted to throw the ball (step 182).

When a change is detected, the application 70 sends a data package tothe management application 32 including data from the accelerometer 60and the digital compass 62 (step 184). The management application 32passes this data to the device 50 f to enable the application 70 toascertain if the user 40 f catches or misses the virtually thrown ball.

The process continues as the users 40 e and 40 f continue to throw thevirtual ball back and forth to each other.

Scenario 3—Printing a Document

The third scenario relates to the print station zone 20. In thisscenario the print station itself is a registered device that hasregistered to provide printing facilities (both color and black andwhite) for registered users in a private printing share group. Theprivate printing share group is limited to employees and invited guestsof the office area 10. However, in other embodiments, a printing stationmay be provided that charges for printing and that is publiclyavailable.

In this scenario, a registered user (for example, user 40 k) is at thevending area 22 and remembers that he would like to print a document.The user 40 k selects the document on his mobile device 50 k, selects aprint option presented on a menu of the application 70, and then makes aflicking motion with his finger across the touchscreen 56. This isdetected by the application 70, which sends a data package to themanagement application 32. In addition to information from the digitalcompass 62 and the GPS device 64, the application 70 also sendsinformation indicating that the user 40 k has requested printing of thedocument.

In this example, there is only one printing station, so this is selectedby the management application 32. In other examples there may bemultiple printing stations, in which case the management application 32will select the one closest to the direction pointed to by the action ofthe user 40 k (provided it is located sufficiently close to the user'sdevice 50 k).

Once the management application 32 has transmitted the document to theprinting station for printing, and once the printing station hasconfirmed successful printing, then the management application 32notifies the application 70 that printing has been successful, and alsoidentifies the printer that was used (either by name or by geographicalposition). The user's mobile device 50 k may direct the user 40 k to theprinter that was used.

Although only three scenarios have been described it will be apparent tothe skilled person that many other scenarios are possible. For example,games may involve card dealing, driving virtual cars, gambling, multipleplayers spread across a large geography, and the like. Other scenariosmay involve transfer of virtual cash, and handing out flyers and/orcoupons to people in a certain location.

Various modifications may be made to the above described embodimentwithin the scope of the invention, for example, in the above embodiment,the user is described as registering with the management application 32,in other embodiments, the user's device may register with the managementapplication 32. This would allow the user to have multiple devicesregistered simultaneously, so that the user could easily move databetween devices (for example, from a mobile phone to a tablet computer).

The layout of the office 10 and the different zones shown are merelyillustrative, and are provided only to give a specific example of thetypes of environment in which embodiments of the invention may beimplemented. Many other types of environment, such as casinos, stadia,and the like, could be given.

One variation of the ball throwing game (virtual catch) described inscenario two above is for the management application 32 to ascertain ifthe receiving mobile device has successfully caught the ball. This mayinvolve the following steps. The owner of device A holds the virtualball. The owner of device B stands close by and is ready to receive theball. The owner of device A moves device A as if he/she was throwing aball. The application on device A calculates the position of device A atthe start and end of the motion and also uses the information fromsensors within device A to allow it to calculate the velocity of thevirtual ball. This information is then packaged into a message and sentto the management application 32. The management application 32, whichis already monitoring the position and movement of both devices (deviceA and B), receives the message and uses the information in the messageto identify if device B will intercept the “ball” or if it is out ofrange. If it is in the correct position the data will be sent to deviceB. Device B processes the received data indicating to the user of deviceB that the virtual ball has been successfully caught. If device B is notin the correct position to receive the virtual ball from device A, thenthe management application 32 sends a failed catch message to device Band also to device A. Device B would indicate to its user that he/shedid not catch the virtual ball. Device A would indicate to its user thatthe other player failed to catch the virtual ball.

The management application 32 may also send status information to deviceB (and device A) throughout the game to highlight the progress of thedata. The users of devices A and B may monitor this data to enable themto move into the “path” of the data to catch the ball.

The steps of the methods described herein may be carried out in anysuitable order, or simultaneously where appropriate. The methodsdescribed herein may be performed by software in machine readable formon a tangible storage medium or as a propagating signal.

The terms “comprising”, “including”, “incorporating”, and “having” areused herein to recite an open-ended list of one or more elements orsteps, not a closed list. When such terms are used, those elements orsteps recited in the list are not exclusive of other elements or stepsthat may be added to the list.

Unless otherwise indicated by the context, the terms “a” and “an” areused herein to denote at least one of the elements, integers, steps,features, operations, or components mentioned thereafter, but do notexclude additional elements, integers, steps, features, operations, orcomponents.

The presence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other similar phrases in some instancesdoes not mean, and should not be construed as meaning, that the narrowercase is intended or required in instances where such broadening phrasesare not used.

The reader's attention is directed to all papers and documents which arefiled concurrently with or previous to this specification in connectionwith this application and which are open to public inspection with thisspecification, and the contents of all such papers and documents areincorporated herein by reference.

What is claimed is:
 1. A method of implementing data transfer from amobile device, the method comprising: (i) receiving, by a server,positional information sent from the mobile device and receiving, by theserver, an orientation of the mobile device and the orientation sentfrom the mobile device, wherein receiving further includes registeringthe mobile device when the mobile device enters an office that definesan interaction environment, receiving a share group creation requestfrom the mobile device and prompting the mobile device for parameters;(ii) receiving, by the server, directional information sent from themobile device, wherein the directional information is ascertained by themobile device using an internal accelerometer, thereby detecting how auser of the mobile device is moving the mobile device and thedirectional information received as at least a portion of the parametersfor the share group creation request, transmitting the portion of theparameters to a management application, receiving a group requestconfirmation from the management application, and notifying the useroperating the mobile device of the group request confirmation; (iii)receiving, by the server, data sent from the mobile device; (iv)ascertaining, by the server, the receiving device based on the receiveddirectional information and the orientation of the mobile device, andascertaining a plurality of receiving devices selected by the user ofthe mobile device in addition to the received directional informationfrom the mobile device, and ascertaining the receiving device based alsoon received velocity and/or acceleration information from the mobiledevice; and (v) providing, by the server, the data received from themobile device to the ascertained receiving device.
 2. A method accordingto claim 1, wherein steps (i) to (iii) are implemented concurrently orin any desired order.
 3. A method according to claim 1, whereinascertaining a receiving device based on the received directionalinformation includes ascertaining a device located in the direction ofmotion provided by the user of the mobile device.
 4. A method accordingto claim 1, wherein providing the data received from the mobile deviceto the ascertained receiving device includes providing the ascertainedreceiving device with an identification of the mobile device.
 5. Amanagement application executing on the server and operable to implementthe steps of claim 1.